The ContractCallBuilder.messages() method incorrectly casts all messages to MessageData without type checking, causing potential runtime errors when handling CosmosTransactionMessage types.

Changes:

• Add type guard ('typeUrl' in message && 'value' in message) before accessing MessageData properties
• Move ExecuteContractMessage handling to fallback path after MessageData checks
• Improve error messages to include message context (index, typeUrl)
• Add validation for Uint8Array decoded messages

Example:

// Before: Unsafe cast without checking
const msg = message as MessageData<CustomMessage>;
const { typeUrl, value } = msg;

// After: Type guard before accessing properties
if ('typeUrl' in message && 'value' in message) {
  const { typeUrl, value } = message as MessageData<CustomMessage>;
  // Handle pre-encoded messages...
}
// Fallback to ExecuteContractMessage

This prevents runtime errors when messages don't conform to the MessageData shape, particularly when mixing typed messages with pre-encoded message formats in group proposals.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.